Since it has same changes from this PR #528 but with +3 new commits please add some text like

@sadeghbarati Didn't realize it until I made the PR sorry for that😅 I modified it to include only the changes for this PR

@MuhammadM1998, another point regarding the shadcn-vue CLI init command, when we execute it in Nuxt projects, it still installs those dependencies. Therefore, ensure to update the cli package too

Oh you're right will push changes later today

@sadeghbarati Refactored the CLI to check if shadcn-nuxt is installed and checks its version to ensure that it handles the dependencies for backward compat.

Let's wait for Zernonia's opinion cause he is the author of this module 💯

Thanks for the PR @MuhammadM1998 ..

One question tho, if user decide to use other version of Radix Vue, how can they install a different version of it?

@zernonia Thanks! Users can use overrides to use a different version.

"dependencies": {
  "shadcn-nuxt": "^3.0.0", // Has radix-vue v1.7.3 as a dependency
},
"overrides": {
  "radix-vue": "^2.0.0", // This version is what will be installed
}

@MuhammadM1998 Let's remove radix-vue from shadcn-nuxt module deps?

Most of the users are unaware of overrides module features in packageManagers

Also, let's consider checking this Nuxt PR too: nuxt/nuxt#27155

If it gets merged we don't need @oxc-parser/wasm anymore I think

@MuhammadM1998 Let's remove radix-vue from shadcn-nuxt module deps?

Most of the users are unaware of overrides module features in packageManagers

Normally a user won't need to use overrides. A case where a user would need that is that shadcn-nuxt bumped radix-vue to 1.7.8 for example and it caused problems for the user so then he'd use overrides to install radix-vue 1.7.7. That's a slim chance as you see. I'm okay with removing it from dependencies (maybe move it to peerDeps?) but imo its better this way. I'll wait for you decision. Feel free to push changes too!

@MuhammadM1998 Let's merge it for now for further PRs 🙏